home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Netware Super Library
/
Netware Super Library.iso
/
nov_info
/
fyi9
/
082213.dos
< prev
next >
Wrap
Text File
|
1990-08-22
|
3KB
|
59 lines
Number: A2DC073190U233
Subject: Error Renaming DRVRDATA.DAT in NETGEN
Date: August 21, 1990
OS Version: 286
Shell Version: Newer than 2.15C
- - - - - - - - - - - - - - - - - - - - - - - - - - -
GENERAL
INFORMATION: A couple of FYIs have been distributed on the following error,
but some confusion regarding the issue still exists. Here
are my findings on the problem.
ERROR: Rename returned an error code of -1
DESCRIPTION: An attempt to rename the file "DRVRDATA.DAT to DRVRDATA.BAK"
failed.
SEVERITY: The current operation cannot be completed.
This error occurs in NETGEN when using a shell newer than
v2.15C. (We have tested up through v3.01 Rev. B.) It only
occurs if the system being generated is v2.15a or older and
the file DRVRDATA.DAT does NOT exist on the SUPPORT directory
(the file does not exist prior to the first generation). You
will see the error after choosing the option "Save Selections
and Continue".
The version of the server you are attached to makes no
difference. We witnessed the same results on v2.15C, v3.0,
and v3.1. The shell is the problem. The return code is being
interpreted incorrectly.
SOLUTION: If this error is encountered, check the SUPPORT directory for
the file DRVRDATA.DAT. The file will not be there. If it is
there, then it is probably corrupted. Rename it and if there
is a DRVRDATA.BAK file. then rename it also. Create the file
using COPY CON. (It doesn't matter how large or what it
contains.) Now, perform a NETGEN -N. (The -N option must be
used or NETGEN will try to read DRVRDATA.DAT!)
This should get them through the initial installation. Now
a valid DRVRDATA.DAT will exist and the problem should no
longer occur.
COMMENTS: Here is a bit of additional information regarding this error.
An additional solution not mentioned in the original message
is to use the v2.15a shell. This version does not have the
problem when trying to open the nonexistent file.
We have also tested the v3.01 Rev. C (BETA) shells. They fail
as well. They report the error described above. The same
work around can be used.
This has been reported to Engineering.
(X) This information was verified in the lab.